QUESTIONS

| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 |

a) John needs to receive an email notification about his purchase. Isabel needs to choose the background color of a webpage. Nathan wants to be able to contact Luisa to use the solution at the same time.
b) 40% of respondents report using process X and 60% report using process Y. The most accessed page, excluding the homepage, was the solution info page. 6% of users say they don't understand how to use an advanced feature.

User stories are a way to describe features or functionalities from the perspective of the end users. Each user story typically follows a format like "As a [type of user], I want [an action or capability] so that [I can achieve a goal or benefit]." User stories help teams understand the needs and requirements of users in a clear and user-centric manner.

In option (a), the statements describe specific user needs and desires:

- John needs to receive an email notification about his purchase.
- Isabel needs to choose the background color of a webpage.
- Nathan wants to be able to contact Luisa to use the solution at the same time.

These statements clearly represent user-centric requirements, making them suitable examples of user stories.

Option (b), on the other hand, provides statistical data and observations related to user behavior and usage patterns. While this information can be valuable for understanding user behavior, it does not directly represent user stories. User stories focus on capturing user needs and motivations in a concise and user-centered format, rather than presenting data or statistics about user actions.

QUESTIONS

| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 |